In `@frontend/src/lib/i18n/locales/ca-ES.json`:
- Around line 54-80: The locale file ca-ES.json currently contains English text
for keys such as "errorSubtitleInfo", "errorSubtitle", "forgotPasswordMessage",
"fieldRequired", "invalidInput", "domainWarningTitle", "domainWarningSubtitle",
"ignoreTitle", "goToCorrectDomainTitle", "authorizeTitle", "authorizeCardTitle",
"authorizeSubtitle", "authorizeSubtitleOAuth", "authorizeLoadingTitle",
"authorizeLoadingSubtitle", "authorizeSuccessTitle", "authorizeSuccessSubtitle",
"authorizeErrorClientInfo", "authorizeErrorMissingParams", "openidScopeName",
"openidScopeDescription", "emailScopeName", "emailScopeDescription",
"profileScopeName", "profileScopeDescription", and
"groupsScopeName"/"groupsScopeDescription"; replace each English string with the
correct Catalan translation for those keys (or, if these are intended
placeholders for later translation, add a clear comment/marker or use Crowdin
placeholder values to indicate they are untranslated) so the ca-ES.json file
contains proper Catalan entries before release.

In `@frontend/src/lib/i18n/locales/cs-CZ.json`:
- Around line 54-80: The Czech locale file left many values in English; update
the keys errorSubtitleInfo, domainWarningTitle/subtitle if needed, ignoreTitle,
goToCorrectDomainTitle, authorizeTitle, authorizeCardTitle, authorizeSubtitle,
authorizeSubtitleOAuth, authorizeLoadingTitle, authorizeLoadingSubtitle,
authorizeSuccessTitle, authorizeSuccessSubtitle, authorizeErrorClientInfo,
authorizeErrorMissingParams, openidScopeName, openidScopeDescription,
emailScopeName, emailScopeDescription, profileScopeName,
profileScopeDescription, groupsScopeName, and groupsScopeDescription with proper
Czech translations; preserve interpolation tokens like {{app}} and
{{missingParams}} and any HTML markup such as <code> exactly as-is, keep JSON
string escaping valid, and ensure you update the values in the cs-CZ.json object
(e.g., keys authorizeCardTitle, authorizeErrorMissingParams) rather than adding
new keys or changing key names.

In `@frontend/src/lib/i18n/locales/da-DK.json`:
- Around line 54-80: Several newly added i18n keys in the Danish locale are
still in English; update the values for errorSubtitleInfo, errorSubtitle,
forgotPasswordMessage, fieldRequired, invalidInput, domainWarningTitle,
domainWarningSubtitle, ignoreTitle, goToCorrectDomainTitle, authorizeTitle,
authorizeCardTitle, authorizeSubtitle, authorizeSubtitleOAuth,
authorizeLoadingTitle, authorizeLoadingSubtitle, authorizeSuccessTitle,
authorizeSuccessSubtitle, authorizeErrorClientInfo, authorizeErrorMissingParams,
openidScopeName, openidScopeDescription, emailScopeName, emailScopeDescription,
profileScopeName, profileScopeDescription, groupsScopeName, and
groupsScopeDescription with proper Danish translations, preserving all
placeholders (e.g., {{appUrl}}, {{currentUrl}}, {{app}}, {{missingParams}}) and
inline markup/backticks exactly as in the originals so templates continue to
render correctly.

In `@frontend/src/lib/i18n/locales/es-ES.json`:
- Line 54: Several keys in the Spanish locale file are still in English (e.g.,
"errorSubtitleInfo" and keys from "authorizeTitle" through
"groupsScopeDescription"); update their values to proper Spanish translations or
mark them as intentionally pending translation. Open
frontend/src/lib/i18n/locales/es-ES.json, locate the keys errorSubtitleInfo and
authorizeTitle ... groupsScopeDescription, and replace the English strings with
accurate Spanish translations (or add a clear TODO comment/metadata indicating
they are queued for Crowdin) so the es-ES locale contains Spanish text or an
explicit fallback note.

In `@frontend/src/lib/i18n/locales/it-IT.json`:
- Around line 54-55: The listed keys are still in English and need Italian
translations: replace the values for "errorSubtitleInfo", "errorSubtitle" and
the block from "authorizeTitle" through "groupsScopeDescription" with proper
Italian text; locate these keys (errorSubtitleInfo, errorSubtitle,
authorizeTitle, authorizeDescription, authorizeConfirm, authorizeCancel,
authorizeScopesTitle, emailScopeDescription, profileScopeDescription,
groupsScopeDescription) in the it-IT locale and provide accurate Italian
translations, preserving punctuation, capitalization and any
interpolation/placeholders exactly as in the originals.

In `@frontend/src/lib/i18n/locales/nl-NL.json`:
- Line 55: The Dutch locale contains an untranslated English value for the key
"errorSubtitle" in nl-NL.json; replace the English string with an appropriate
Dutch translation (for example: "Er is een fout opgetreden bij het uitvoeren van
deze actie. Controleer de console voor meer informatie.") by updating the
"errorSubtitle" value so it matches the surrounding translated keys.

In `@frontend/src/lib/i18n/locales/no-NO.json`:
- Around line 62-80: The no-NO locale file currently contains English values for
keys such as "goToCorrectDomainTitle", "authorizeTitle", "authorizeCardTitle",
"authorizeSubtitle", "authorizeSubtitleOAuth", "authorizeLoadingTitle",
"authorizeLoadingSubtitle", "authorizeSuccessTitle", "authorizeSuccessSubtitle",
"authorizeErrorClientInfo", "authorizeErrorMissingParams", "openidScopeName",
"openidScopeDescription", "emailScopeName", "emailScopeDescription",
"profileScopeName", "profileScopeDescription", and
"groupsScopeName"/"groupsScopeDescription"; replace each English string with
proper Norwegian Bokmål translations for these keys (or, if you intend this to
be a placeholder until Crowdin provides translations, add a clear comment/flag
in the file indicating it is a placeholder and should not be treated as a
complete translation set) so the no-NO.json contains real Norwegian values or an
explicit placeholder marker.

In `@frontend/src/lib/i18n/locales/pt-BR.json`:
- Line 54: The pt-BR locale key "errorSubtitleInfo" currently contains an
English string; update its value to a proper Brazilian Portuguese translation
(e.g., "Ocorreu o seguinte erro ao processar sua solicitação:"), replacing the
English text so the pt-BR.json entry for errorSubtitleInfo is fully translated.
- Around line 63-80: Translate the untranslated English strings in the pt-BR
locale for the authorization and scope block: replace values for keys
authorizeTitle, authorizeCardTitle, authorizeSubtitle, authorizeSubtitleOAuth,
authorizeLoadingTitle, authorizeLoadingSubtitle, authorizeSuccessTitle,
authorizeSuccessSubtitle, authorizeErrorClientInfo, authorizeErrorMissingParams,
openidScopeName, openidScopeDescription, emailScopeName, emailScopeDescription,
profileScopeName, profileScopeDescription, groupsScopeName, and
groupsScopeDescription with accurate Brazilian Portuguese translations
preserving interpolation tokens like {{app}} and {{missingParams}} and keeping
punctuation and capitalization consistent with the rest of the file.

In `@frontend/src/lib/i18n/locales/ro-RO.json`:
- Around line 54-80: The ro-RO locale file currently contains English text for
every key (e.g., "errorSubtitleInfo", "forgotPasswordMessage",
"authorizeSubtitleOAuth", "openidScopeDescription", "groupsScopeDescription");
replace each English value with the correct Romanian translation for those keys
(or mark them explicitly as TODO/untranslated if you intend to keep
scaffolding), ensuring translations cover all keys in the diff
(errorSubtitleInfo, errorSubtitle, forgotPasswordMessage, fieldRequired,
invalidInput, domainWarningTitle, domainWarningSubtitle, ignoreTitle,
goToCorrectDomainTitle, authorizeTitle, authorizeCardTitle, authorizeSubtitle,
authorizeSubtitleOAuth, authorizeLoadingTitle, authorizeLoadingSubtitle,
authorizeSuccessTitle, authorizeSuccessSubtitle, authorizeErrorClientInfo,
authorizeErrorMissingParams, openidScopeName, openidScopeDescription,
emailScopeName, emailScopeDescription, profileScopeName,
profileScopeDescription, groupsScopeName, groupsScopeDescription) so Romanian
users see localized UI or the file clearly indicates it’s intentionally
untranslated.

In `@frontend/src/lib/i18n/locales/ru-RU.json`:
- Around line 54-80: The Russian locale contains several untranslated English
strings; replace them with Russian translations for keys errorSubtitleInfo,
authorizeTitle, authorizeCardTitle (preserve {{app}}), authorizeSubtitle,
authorizeSubtitleOAuth, authorizeLoadingTitle, authorizeLoadingSubtitle,
authorizeSuccessTitle, authorizeSuccessSubtitle, authorizeErrorClientInfo,
authorizeErrorMissingParams (preserve {{missingParams}}), and the scope keys
openidScopeName, openidScopeDescription, emailScopeName, emailScopeDescription,
profileScopeName, profileScopeDescription, groupsScopeName,
groupsScopeDescription so the UI is fully localized for ru-RU; ensure
placeholders like {{app}} and {{missingParams}} are kept intact and phrasing
matches existing Russian tone.

In `@frontend/src/lib/i18n/locales/sr-SP.json`:
- Around line 54-80: The new localization keys (errorSubtitleInfo,
goToCorrectDomainTitle, authorizeTitle, authorizeCardTitle, authorizeSubtitle,
authorizeSubtitleOAuth, authorizeLoadingTitle, authorizeLoadingSubtitle,
authorizeSuccessTitle, authorizeSuccessSubtitle, authorizeErrorClientInfo,
authorizeErrorMissingParams, openidScopeName, openidScopeDescription,
emailScopeName, emailScopeDescription, profileScopeName,
profileScopeDescription, groupsScopeName, groupsScopeDescription) are still in
English; update their values to Serbian or add them to the Crowdin translation
queue so translators can provide Serbian strings—ensure you modify the JSON
entries (e.g., "errorSubtitleInfo": "...") with the translated text or mark them
for translation in the i18n workflow.

In `@frontend/src/lib/i18n/locales/sv-SE.json`:
- Around line 54-80: The Swedish locale file contains many untranslated English
strings (e.g., "errorSubtitleInfo", "errorSubtitle", "forgotPasswordMessage",
"fieldRequired", "invalidInput", "domainWarningTitle", "domainWarningSubtitle",
"ignoreTitle", "goToCorrectDomainTitle", "authorizeTitle", "authorizeCardTitle",
"authorizeSubtitle", "authorizeSubtitleOAuth", "authorizeLoadingTitle",
"authorizeLoadingSubtitle", "authorizeSuccessTitle", "authorizeSuccessSubtitle",
"authorizeErrorClientInfo", "authorizeErrorMissingParams", "openidScopeName",
"openidScopeDescription", "emailScopeName", "emailScopeDescription",
"profileScopeName", "profileScopeDescription", "groupsScopeName",
"groupsScopeDescription") that need Swedish translations; replace the English
values with proper Swedish translations for each key or confirm they are
submitted to the translation pipeline (Crowdin) and add placeholder markers if
necessary so the app can detect untranslated entries, then commit the updated
sv-SE.json with translated strings or translation-status markers.

In `@frontend/src/lib/i18n/locales/tr-TR.json`:
- Around line 54-55: The two keys errorSubtitleInfo and errorSubtitle in the
Turkish locale still contain English text; update their values to proper Turkish
translations so the tr-TR.json is consistent (replace the English strings for
errorSubtitleInfo and errorSubtitle with appropriate Turkish sentences conveying
"The following error occurred while processing your request:" and "An error
occurred while trying to perform this action. Please check the console for more
information.").
- Around line 63-80: The Turkish locale file contains untranslated English
strings for the authorize and scope entries; replace the values for keys
authorizeTitle, authorizeCardTitle, authorizeSubtitle, authorizeSubtitleOAuth,
authorizeLoadingTitle, authorizeLoadingSubtitle, authorizeSuccessTitle,
authorizeSuccessSubtitle, authorizeErrorClientInfo, authorizeErrorMissingParams,
openidScopeName, openidScopeDescription, emailScopeName, emailScopeDescription,
profileScopeName, profileScopeDescription, groupsScopeName, and
groupsScopeDescription with proper Turkish translations, preserving any
placeholders like {{app}} and {{missingParams}} exactly as-is and keeping
punctuation and capitalization consistent with the rest of the file.
- Line 25: The translation string continueInsecureRedirectSubtitle currently
reads "from <code>http</code> to <code>http</code>" which is incorrect; update
the value for continueInsecureRedirectSubtitle in tr-TR.json so the source
protocol is <code>https</code> (i.e., change the first <code>http</code> to
<code>https</code>) to match the English source and other locales.

In `@frontend/src/lib/i18n/locales/uk-UA.json`:
- Around line 54-55: The Ukrainian locale file has untranslated English values
for keys errorSubtitleInfo, errorSubtitle, authorizeTitle, authorizeSubtitle,
authorizeConfirm, authorizeCancel, authorizeCheckbox, scopesTitle, scopeMessages
(and the specific scope keys docsScope, filesScope, tokensScope, groupsScope,
groupsScopeDescription); replace the English strings for these keys with
accurate Ukrainian translations, preserving the JSON key names and punctuation,
ensuring proper UTF-8 encoding/escaping and trailing commas remain valid JSON,
and run the i18n/locale lint or build to verify no syntax or missing-key errors.

In `@frontend/src/lib/i18n/locales/vi-VN.json`:
- Around line 54-80: Most new keys in vi-VN.json (e.g., "errorSubtitleInfo",
"authorizeTitle", "authorizeCardTitle", "authorizeSubtitle",
"authorizeSubtitleOAuth", "authorizeLoadingTitle", "authorizeLoadingSubtitle",
"authorizeSuccessTitle", "authorizeSuccessSubtitle", "authorizeErrorClientInfo",
"authorizeErrorMissingParams", "openidScopeName", "openidScopeDescription",
"emailScopeName", "emailScopeDescription", "profileScopeName",
"profileScopeDescription", "groupsScopeName", "groupsScopeDescription") are
still in English; replace those values with proper Vietnamese translations or
explicitly mark them for translation in Crowdin so they don't ship untranslated,
and confirm the Crowdin config will ingest this vi-VN.json path (or add the keys
to the Crowdin source) so translators see them.

In `@frontend/src/lib/i18n/locales/zh-CN.json`:
- Line 54: The zh-CN locale file contains untranslated English values for keys
like "errorSubtitleInfo", "authorizeTitle", "authorizeCardTitle" and the
scope-related keys (lines ~63-80); update each of these keys in
frontend/src/lib/i18n/locales/zh-CN.json with appropriate Simplified Chinese
translations (or replace with a clear TODO/placeholder marker if you
intentionally defer translation) and ensure you add them to your translation
tracking (e.g., Crowdin) so they don’t ship untranslated.

In `@frontend/src/lib/i18n/locales/zh-TW.json`:
- Around line 54-80: Several keys in zh-TW are still English (e.g.,
"errorSubtitleInfo" and the
authorize*/openidScope*/emailScope*/profileScope*/groupsScope* keys); either
provide Traditional Chinese translations for those keys ("errorSubtitleInfo",
"authorizeTitle", "authorizeCardTitle", "authorizeSubtitle",
"authorizeSubtitleOAuth", "authorizeLoadingTitle", "authorizeLoadingSubtitle",
"authorizeSuccessTitle", "authorizeSuccessSubtitle", "authorizeErrorClientInfo",
"authorizeErrorMissingParams", "openidScopeName", "openidScopeDescription",
"emailScopeName", "emailScopeDescription", "profileScopeName",
"profileScopeDescription", "groupsScopeName", "groupsScopeDescription") or
remove those entries from the zh-TW JSON so i18next can fall back to the default
locale until proper translations are available. Ensure any replacements use
correct Traditional Chinese phrasing and keep interpolation tokens like {{app}}
and {{missingParams}} intact.